Skip to content

Add patient information factsheet vertical slice#794

Closed
BigSimmo wants to merge 9 commits into
mainfrom
cursor/patient-factsheets-db17
Closed

Add patient information factsheet vertical slice#794
BigSimmo wants to merge 9 commits into
mainfrom
cursor/patient-factsheets-db17

Conversation

@BigSimmo

Copy link
Copy Markdown
Owner

Summary

  • Adds a patient-facing factsheet vertical slice: browse, search, and printable/shareable detail pages under /factsheets/*, using clearly labelled sample content.
  • Fixes lint (no sync setState-in-effect) and site-map ordering for the new routes.
  • Supersedes Add patient information factsheet vertical slice (home, search, detail) #751 (original blocked on PR policy and lint/sitemap CI).

Verification

  • Hosted Build / Advisory UI / Production UI on the predecessor head.
  • Local ESLint on factsheets-search-page and site-map unit tests passed after the CI fix.
  • npm run verify:ui evidence via hosted Production UI.

Risk and rollout

  • Risk: low; new routes serve sample content explicitly labelled as non-clinical; no live data, API, or RAG path changes.
  • Rollback: revert this PR; /factsheets routes are removed.
  • Provider or production effects: None

Clinical Governance Preflight

  • Source-backed claims still require linked source verification before clinical use
  • No patient-identifiable document workflow was introduced or expanded without explicit governance approval
  • Supabase target remains Clinical KB Database (sjrfecxgysukkwxsowpy)
  • Service-role keys and private document access remain server-only
  • Demo/synthetic content remains clearly separated from real clinical sources
  • Source metadata, review status, and outdated/unknown-source behavior remain conservative
  • Deployment classification/TGA SaMD impact was checked when clinical decision-support behavior changed
Open in Web Open in Cursor 

BigSimmo and others added 5 commits July 18, 2026 03:26
- factsheets-search-page: replace synchronous setState-in-effect with
  the 'adjusting state during rendering' pattern for input sync; remove
  the artificial loading state (search is synchronous over in-memory
  data). Fixes two @eslint-react/hooks-extra lint errors.
- generate-site-map: register /factsheets, /factsheets/[slug], and
  /factsheets/search descriptions in routeDescriptions so the generator
  emits proper descriptions instead of 'Route discovered from app
  directory'.
- docs/site-map.md: correct entry order so factsheets/* sorts before
  favourites (alphabetical localeCompare). Fixes tests/site-map.test.ts.
@supabase

supabase Bot commented Jul 17, 2026

Copy link
Copy Markdown

This pull request has been ignored for the connected project sjrfecxgysukkwxsowpy because there are no changes detected in supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.


Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.

@cursor
cursor Bot enabled auto-merge (squash) July 17, 2026 20:36
@coderabbitai

coderabbitai Bot commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Warning

Review limit reached

@cursor[bot], you've reached your PR review limit, so we couldn't start this review.

Next review available in: 13 seconds

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 74bcb4d3-942b-496a-aa2d-197ecd12a919

📥 Commits

Reviewing files that changed from the base of the PR and between 3ff8095 and 9984c92.

📒 Files selected for processing (12)
  • docs/site-map.md
  • scripts/generate-site-map.ts
  • src/app/factsheets/[slug]/page.tsx
  • src/app/factsheets/layout.tsx
  • src/app/factsheets/page.tsx
  • src/app/factsheets/search/page.tsx
  • src/components/factsheets/factsheet-detail-page.tsx
  • src/components/factsheets/factsheet-shell.tsx
  • src/components/factsheets/factsheets-data.ts
  • src/components/factsheets/factsheets-home-page.tsx
  • src/components/factsheets/factsheets-search-page.tsx
  • tests/factsheets-data.test.ts
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch cursor/patient-factsheets-db17

Comment @coderabbitai help to get the list of available commands.

@BigSimmo BigSimmo closed this Jul 18, 2026
auto-merge was automatically disabled July 18, 2026 06:22

Pull request was closed

@BigSimmo
BigSimmo deleted the cursor/patient-factsheets-db17 branch July 18, 2026 18:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants